-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-127353: Allow to force color output on Windows V2 #127926
Conversation
@hugovk, could you check this PR please? |
🤖 New build scheduled with the buildbot fleet by @ZeroIntensity for commit a50e877 🤖 If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good so far!
The two current buildbot failures are unrelated and also happen elsewhere, and there might be a third unrelated to come, but all the other buildbots are now passing. 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
This is now passing on all the buildbots, except for two which are unrelated (it's #125588 (comment)).
Thanks @PalmtopTiger for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…127926) (cherry picked from commit 0ac40acec045c4ce780cf7d887fcbe4c661e82b7) Co-authored-by: Andrey Efremov <[email protected]>
GH-127944 is a backport of this pull request to the 3.13 branch. |
Let's hope this doesn't break anything else! |
Yeah, will wait until tomorrow before merging the backport :) |
This PR allows to force color output on Windows and brings the behavior of can_colorize function into compliance with POSIX. Second version of #127354 with fixed tests.